-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat!: upgrade forc@0.58.0
and remove V0
encoding
#2238
Conversation
…/feat/deprecate-v0
…els-ts into db/feat/deprecate-v0
…/feat/deprecate-v0
V0
encodingforc@0.57.0
and remove V0
encoding
…/feat/deprecate-v0
✨ A PR has been created under the |
forc@0.57.0
and remove V0
encodingforc@0.58.0
and remove V0
encoding
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great - some small comments 🚀 🌔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome work! Left some suggestions
Coverage Report:
Changed Files:
|
Closes #2041
Closes #2109
Closes #2005
Closes #922
This PR:
forc
to0.58.0
V1
encoding for configurable constantsV0
encodingV0
V0
codersV1
tests as everything is coveredpadToWordSize: boolean
encoding option for use inside transactions fornumber
andboolean
valuesBreaking Changes:
We no longer support
V0
encoding, meaning the version itself and it's encoding options can no longer be passed toAbiCoder
.